-
-
Notifications
You must be signed in to change notification settings - Fork 497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to GCC 10, clang 12 #2010
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We've been using major compiler versions to demark psuedo-epochs in the compiler stack in order to help ease the transitions to new features/packages. For example, we did this with the sysroot work.
Before we do this, is there anything we want to bump and/or change?
I can't think of anything to change. |
Based on how I read the compatibility matrix for CUDA, this could (should?) also bump to GCC 10 for CUDA 11.1+ |
Co-authored-by: jakirkham <jakirkham@gmail.com>
I have an open comment how we can/should deal with this in staged recipes (the answer may be "do nothing", though then we'd either have to stay on GCC 9 or drop CUDA <=11.0 in staged recipes, unless I'm overlooking something somewhere...). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment resolved, looking forward to this!
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)